home *** CD-ROM | disk | FTP | other *** search
- Path: news.u.washington.edu!djarvis
- From: djarvis@u.washington.edu (David Jarvis)
- Newsgroups: comp.sys.amiga.networking
- Subject: Re: Dialer for mlink
- Date: 2 Mar 1996 03:11:47 GMT
- Organization: University of Washington, Seattle
- Message-ID: <4h8e9j$q25@nntp5.u.washington.edu>
- References: <4h2snt$4dt@news.uni-c.dk> <4h70ci$r3a@pan.otol.fi>
- NNTP-Posting-Host: homer06.u.washington.edu
- NNTP-Posting-User: djarvis
-
- In article <4h70ci$r3a@pan.otol.fi>, Lauri Aalto <aalto@lyseo.otol.fi> wrote:
- >Henrik Lauridsen (hlau@dou.dk) wrote:
- >> I need a dialer to use with Mlink. Right now I'm calling my unixsystem
- >> using Jrcomm, I have to log on and start mlink manually. I would like to
- >> be able to start a script that will call my system, logs on and starts
- >> mlink without any input from me. Does such a program exist?
- >
- >Yes. Try dialer.device for instance. It's a pseudo device which passes
- >data to the actual device (serial.device or whatever you've configured)
- >after it has dialed up and got through the login procedure you've
- >configured. comm/net/dialerdevice17.lha on Aminet.
- >
-
- Just a tip with dialer.device (which I use with MLink also). Try it
- first using the default settings of serial.device, unit and baud. Once
- you get that going, which goes pretty quick, then experiment.
-
- David Jarvis
-
- --
- >>>>>>>>>> On Indian Time - Go Around (Bumper sticker) <<<<<<<<<<
- * I'm just a student - I do not represent the UW or Washington State DOH *
- * My Pneumococcus study, Redstone powwows, & Osage Nation pics on Web pg *
- * djarvis@u.washington.edu or http://weber.u.washington.edu/~djarvis *
-